A carrier (vessel or train) visit goes through a series of phases from the time you create it in N4 to the time you complete the work for the carrier and it departs the facility. You must manually advance a carrier visit through these phases to perform the operations associated with each phase.
N4 uses the following carrier visit phases:
Created: The initial phase for a new carrier visit that you add in N4
In this phase, you can set up container and other data, such as holds/permissions, but the data is not available to XPS.
A carrier visit must be at least in the Created phase to receive EDI messages, such as BAPLIE stow plan messages, without generating an error.
Inbound: The phase when N4 makes the carrier visit and container data available for planning in XPS
You can plan loads and discharges during this phase.
Canceled: The phase that indicates that you canceled a carrier visit before the carrier arrived at the facility
You can advance to this phase only from the Created phase. When you cancel a carrier (vessel or train) visit, the carrier and container data is removed from XPS.
If you receive an EDI message, such as a rail consist, for a carrier in the Canceled phase, N4 rejects the EDI message and displays an error.
Arrived: The phase when the carrier is at the facility and work can start
In this phase, you can load and discharge containers.
Working: The phase when the load and discharge operations are in progress
For vessel visit, the Visit Reference field in the Vessel Load and Vessel Discharge forms lists only the vessel visits that are either in the Arrived or in the Working phase.
For train visits, the Rail Visit Reference field in the Rail Load (on page 1) and Rail Discharge (on page 1) forms lists only the train visits that are either in the Arrived or in the Working phase.
Complete: The phase when you have completed the load and discharge operations for the selected carrier visit
In the Inbound Train Inventory form (on page 1), you cannot select a train visit that is in the Complete or Canceled phase.
Departed: The phase when the carrier has left the facility
When an outbound train visit is advanced to the Departed phase, N4 marks all the railcars associated with the outbound train as Inactive. In XPS client, these railcars are listed in the Delivered cars list but not in the Available cars list.
If you receive or plan containers for a carrier visit in the Departed phase, N4 displays a warning.
For a train visit, do the following:
Use the Actions
Recall Train option to recall a train visit in the Departed phase.
When you recall a train visit, N4 sets the visit phase as Complete and allows you to correct any erroneous data. You cannot recall a train visit if the number of days since the train departed the facility is more than the number of days that you specified in the RLRAIL003 configuration setting. For more information on configuration settings, see Settings view.
Closed: The phase that indicates that you have closed the carrier visit
Carrier and container data is no longer available in XPS.
For a vessel visit, in the Hold/Release Inbound Unit or Stow Plan forms, the Visit Reference field does not list the vessel visits that are either in the Canceled, Complete, Departed, or Closed phase.
Archived: The phase when N4 removes the carrier visit from the list view and you can no longer view, edit, or recall the carrier visit
You cannot receive EDI messages and the carrier and container data is no longer available in XPS.
For a vessel visit, use the Actions
Unarchive Vessel Visit option to unarchive a vessel visit.
Notes
We strongly recommend that you advance a vessel visit from the Departed to the Closed phase two days after a vessel departs to ensure that containers onboard the departed vessel are removed from the list views in XPS. However, the container information remains available in N4. Keeping the vessel visit in the Departed state for two days enables XPS to include vessel load moves for recently departed vessels in any daily EC reports that it generates. If you keep vessel visits in the Departed phase for a long time after the vessel has departed, thousands of departed containers will clutter up the list view in XPS. This may slow down XPS client startups, searches, and equipment control.